Conversation
zchee
force-pushed
the
gha/conformance
branch
8 times, most recently
from
910847b to
672f6fe
Compare
Signed-off-by: Koichi Shiraishi <zchee.io@gmail.com>
tsubakiky
approved these changes
May 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new GitHub Actions workflow to automate conformance testing for both server and client modes. It also includes configuration updates to handle known flaky tests for the client.
New GitHub Actions Workflow for Conformance Testing:
.github/workflows/conformance.yaml: Added a new workflow named "Conformance" to run conformance tests onpush,pull_request, and manual triggers. The workflow includes two jobs:uv, installs the project, and runs theconnectconformancetool in server mode.connectconformancetool in client mode with additional handling for known flaky tests.Configuration for Known Flaky Tests:
conformance/client_known_flaky.yaml: Added a configuration file to specify known flaky tests for the client, starting with theClient Cancellation/**test case.